Validate Next.js version #46
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ehmicky
added
the
type: feature
Closed
lindsaylevine
approved these changes
Nov 17, 2020
ascorbic
pushed a commit
that referenced
this pull request
Oct 14, 2021
serhalp
pushed a commit
that referenced
this pull request
Apr 5, 2024
* feat: add FETCH cache Fixes https://linear.app/netlify/issue/FRA-60/implement-get-and-set * chore: close the connection * chore: update * chore: update * chore: increase lambda timeout * chore: fix tests * chore: cleanup * chore: cleanup and splitup for better performance * chore: update * chore: update * chore: build custom test sharding as the fetch test needs to run on it's own executor due to side effects of next.js patching the fetch function * chore: update
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #25
This adds some validation checks to ensure that users are not using an old version of Next.js.
This also prints a warning for users with Next.js 10.